What Changed

• Updated trace diagnostics NDJSON line parsing to use the shared decodeJsonResult(Schema.Record(...)) helper instead of JSON.parse.
• Kept trace timestamp parsing and aggregate span bounds as Option values internally until returning the diagnostics result.
• Updated process diagnostics so ProcessRow.pgid is represented as an Option and Windows PowerShell JSON parsing goes through Effect Schema decoding.
• Added Windows process parsing coverage and updated process diagnostics tests to use assert from @effect/vitest.

Why

These changes address focused places where diagnostics code was already Effect-based but still used ad-hoc JSON parsing and nullable internal fields. Using Schema-backed JSON decoding and Option makes the parsing boundaries more testable and consistent with the rest of the Effect codebase while preserving the existing soft-fail diagnostics behavior.

UI Changes

Not applicable; this is a server diagnostics refactor with no UI changes.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

Validation:

• pnpm exec vp test run src/diagnostics/TraceDiagnostics.test.ts src/diagnostics/ProcessDiagnostics.test.ts src/diagnostics/ProcessResourceMonitor.test.ts (from apps/server) — 17 tests passed
• pnpm exec vp check --fix — passed with existing warnings
• pnpm exec vp run typecheck — passed